home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
045a
/
jerome.zip
/
JEROME.DOC
< prev
next >
Wrap
Text File
|
1991-10-11
|
83KB
|
1,761 lines
JEROME UTILITIES DEMONSTRATION DISKETTE
BE ADVISED THAT THIS DEMONSTRATION PRODUCT WILL DEVELOPE LIMITATIONS OVER TIME.
THIS DISKETTE CONTAINS DEMO VERSIONS OF THE JEROME UTILITIES PRODUCT. ALL
PROGRAMS ON THIS DISKETTE WILL LOOSE FUNCTIONALITY AFTER 12-31-91!
Software for NetWare with IBM and compatible PCs
USER'S MANUAL
1991 Jerome Computing. All rights reserved. This document may be stored and
destributed as part of the Jerome Utilities Demonstration Diskette. No part of
this publication may be otherwise reproduced, photocopied, stored on a retrieval
system, or transmitted without the express prior written consent of Jerome
Computing, P. O. Box 374, Provo, UT 84603, USA
Throughout this document the following trade marks are mentioned. Jerome
Utilities is a trade mark of Jerome Computing. NetWare and Novell are
registered trademarks of Novell, Inc. IBM is a registered trade mark of
International Business Machines Corporation.
ACKNOWLEDGMENTS
In addition to the creative programming work of Adam Jerome, we express
appreciation for the contributions of George Frey, Herbert Smyth, and Virgil
Smith in the preparation, publication, and distribution of the Jerome Utilities
manual and diskette.
This document and accompaning software are products of the United States of
America.
DEMO LICENSE AGREEMENT
The Jerome Utilities programs are proprietary products of Jerome Computing, and
are protected by United States copyright law and by International Treaty
provisions. Jerome Computing retains title to and ownership of the programs.
BE ADVISED THAT THIS DEMONSTRATION PRODUCT WILL DEVELOPE LIMITATIONS OVER TIME.
The demonstration diskette may be coppied freely with the following
stipulations:
1. All demonstration disk files must be distributed together. No files on this
demostration diskette may be distrubuted individually.
2. Programs may be installed on fileservers, and may be used on all nodes that
have a logical attachment to that fileserver. Demo licence does not grant any
rights to use demonstration programs on a "stand-alone" computer that is not
physically connected to and logged into a NetWare Fileserver.
3. Demo Product may not be sold. Bulletin board operators may charge a small
fee for downloading the product to customers, but may not sell this product.
4. The right to use the demo programs may not be rented or leased.
5. The program code may not be decompiled, disassembled, reverse engineered, or
in any way modified without the prior written consent of Jerome Computing.
6. Jerome Computing reserves the right to revise this publication and to make
changes in its content at any time, without obligation to notify any person or
entity of such revisions or changes.
Further, Jerome Computing makes no representations or warranties with respect to
any Jerome Utilities software, and specifically disclaims any express or implied
warranties of merchantability or fitness for any particular purpose. Further,
Jerome Computing reserves the right to make changes to any and all parts of
Jerome Utilities software and user manuals, at any time, without obligation to
notify any person or entity of such changes.
Except for the express warranties in paragraph 6 above, Jerome Computing grants
no other warranties, express or implied, regarding the disk or related
materials, their fitness for any purpose, their quality, their merchantability,
or otherwise. In no event will Jerome Computing be liable to the purchaser for
any other damages, including but not limited to loss of profit, special,
incidental, or consequential damages arising out of use or inability to use the
programs, even if Jerome Computing or an authorized Jerome Computing
representative has been advised of the possibility of such damages, or for any
claim by any other party.
GOVERNING LAW
This statement shall be construed, interpreted and governed by the laws of the
state of Utah.
INTRODUCTION
This manual--and more--is largely available on context-sensitive help screens.
Jerome Utilities Highlights
JeromeMenu
JeromeMenu (JM) is a user-friendly application menu. JM creates and executes
DOS Batch files.
JeromeEdit
JeromeEdit (JEDIT) is a user-friendly text editor, and is ideal for editing
small files, such as Autoexec.Bat, Config.Sys, and login scripts.
DO
DO is a DOS Command/Batch/login script-enhancement utility. It is used to
enhance user screens, present random thoughts, and other "bells and
whistles."
JeromeMessage
JMESSAGE & JMSGCON are message utilities for NetWare.
JMSGCON is used by a network manager to define messages to be displayed. It
is usually executed by network managers.
JMESSAGE is used by network users to display messages. It is usually
executed by network users from the DOS command line or login scripts.
JLOGOUT
JLOGOUT is a Logout script executor for NetWare. It may be executed in place
of NetWare's LOGOUT command.
NetList
NetList is a NetWare report generator. It is used to generate reports from
the fileserver bindery. It may be used to get a complete list of users,
groups, and other bindery objects.
ATTACHED
ATTACHED is a DOS Command/Batch/script-enhancement utility for NetWare. It
is used to verify a workstation's logical connection to a specified
fileserver.
FLUSHKB
FLUSHKB is a DOS Command/Batch-enhancement utility. It is used to flush
characters from the computer's keyboard buffer.
MEMBER
MEMBER is a DOS Command/Batch/script-enhancement utility for NetWare. It is
used to verify a user's membership in a NetWare group.
REBOOT
REBOOT is a DOS Command/Batch-enhancement utility. It is used to restart a
computer from a "Power-on" state.
RERUN
RERUN is a DOS Command/Batch-enhancement utility. It is used to re-execute a
program a given number of times.
STUFFKB
STUFFKB is a DOS Command/Batch-enhancement utility. It is used to stuff
characters into the computer's keyboard buffer.
System Requirements
100% compatible with DOS 3.3
100% IBM PC/XT/AT-compatible computer.
Novell NetWare
Installation Instructions
Create a directory on the NetWare fileserver.
Example: F:\>MD JEROME
Copy the Jerome Utilities to the directory.
Example: F:\>COPY A:\. F:\JEROME
Flag all the files Sharable.
(F:\>CD JEROME)
NW 2.x Example: F:\JEROME>FLAG *.* S
NW 3.x Example: F:\JEROME>FLAG *.* Ro +S
Map a search drive to the directory in the SYSTEM LOGIN SCRIPT.
Example: MAP S16:=SYS:JEROME
Allocate rights to the directory.
NW 2.x Example: F:\>GRANT R O S FOR SYS:JEROME TO EVERYONE
NW 3.x Example: F:\>GRANT R F FOR SYS:JEROME TO EVERYONE
Installation complete!
PROGRAMS
JeromeMenu
JeromeMenu (JM) is a user-friendly application menu. JM is NOT a TSR
(Terminate, Stay-resident) program, and does not tie up computer memory. JM
creates and executes DOS Batch files.
Using JM:
JeromeMenu is usually activated by either a NetWare login script or by the user
from the DOS command prompt. From a NetWare login script, JeromeMenu is
activated by the EXIT statement.
Example: EXIT "JM"
From the DOS command prompt, Jerome Menu is activated by typing JM.
Example: F:\>JM
JM Tutorial
JM Application Selection Screen:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:43 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░╔════════════════════════════════════════════════════════════════════════╗░░░
░░░║ New Menu ║░░░
░░░╠════════════════════════════════════════════════════════════════════════╣░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░╚════════════════════════════════════════════════════════════════════════╝░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Throughout the JM windows, press the F1 key for HELP. Use cursor keys to move
through the window fields. Press F1 from the HELP screen for key assignments on
your computer.
If you have a mouse, and mouse drivers are loaded, a mouse cursor will be
displayed on the screen. The mouse cursor may be used to highlight and select
JM options.
From the above window, press ESC to exit JM program and return to DOS command
line.
To insert a new entry on the menu, press the INSERT (INS) key. An insert window
will appear:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:43 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║ Menu Text: 15 20 25 30 35 40 45 50 55 60 65 70 ║
║ ║
║ ║
║ Batch Commands: ... ║
╚══════════════════════════════════════════════════════════════════════════════╝
░░░╠════════════════════════════════════════════════════════════════════════╣░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░╚════════════════════════════════════════════════════════════════════════╝░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
At the "Menu Text" prompt, type the menu description of this menu entry. (The
following example describes how to add a new menu selection that will display
your DOS version):
EXAMPLE:
╔════════════════════════════════════════════════════════════════════════════╗
║ Menu Text: 15 20 25 30 35 40 45 50 55 60 65 70 ║
║ Display DOS Version_______________________________________________________ ║
║ ║
║ Batch Commands: ... ║
╚════════════════════════════════════════════════════════════════════════════╝
After describing the Menu text, press ENTER/RETURN ( ). The cursor will jump
to the "Batch Commands:" prompt. Press do display the batch command editor.
The first line of the editor will already have the line @ECHO OFF. Add commands
to this window just as you would in a batch file, or from a DOS prompt.
Example:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:43 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║ Menu Text: 15 20 25 30 35 40 45 50 55 60 65 70 ║
║ Display DOS Version ║
╔══════════════════════════════════════════════════════════════════════════════╗
║ Batch Commands: ║
╠══════════════════════════════════════════════════════════════════════════════╣
║@ECHO OFF ║
║VER ║
║PAUSE ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
When you are done, press Escape (ESC) to exit this screen. JM will display a
"SAVE CHANGES" prompt, to which you should normally respond: YES.Press ESC again
to return to the APPLICATION SELECTION screen. The new application will be
listed on the menu. Other applications may be inserted in the same way.
Example:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:44 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░╔════════════════════════════════════════════════════════════════════════╗░░░
░░░║ New Menu ║░░░
░░░╠════════════════════════════════════════════════════════════════════════╣░░░
░░░║ │Display DOS Version ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░║ │ ║░░░
░░░╚════════════════════════════════════════════════════════════════════════╝░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
To select an application from the menu list, highlight the application using
cursor arrow keys, and press . (Mouse buttons also supported.)
When the selected application terminates, the menu will be redisplayed.
To modify an applications batch file, highlight the application and press F3.
To remove an application from the JM applications list, press DEL.
Advanced Topics & Installation Options
1. Changing Menu Title
To change the menu title, use the -S switch.
Example: C:\>JM -S
This switch will cause a SETUP window to be displayed. Change the menu title as
desired, and press . Press ESC to exit to the application selection screen.
2. JMENU.DAT File
JM creates a file called JMENU.DAT. This file contains the menu entries that
appear on the JM application selection screen. It also contains the JM title,
and application batch commands.
JMENU.DAT is usually located in the users MAIL directory, (the same directory in
which the user's login script is kept).
To override the default, use the -F switch. (Note that both the path and
filename must be specified):
Example: C:\>JM -Fc:\games\JMENU.DAT
3. JMENU$$$.BAT
When an application is executed from JM, a batch file called JMENU$$$.BAT is
created. This is a special batch file used to execute the selected application.
It also contains information needed by JM, in order to highlight the correct
application upon application termination. When the user selects to exit JM, and
return to DOS, JMENU$$$.BAT is erased.
JMENU$$$.BAT is usually located in the user's mail directory. For JM to
function correctly, the Z: drive must be mapped to a directory on the SYS
volume, (any directory on the SYS volume).
To override the default location, use the DOS SET command, and indicate a new
location for JMENU$$$.BAT.
Examples: (DOS) C:\>SET JMPATH=C:\JEROME
(Login Script) DOS SET JMPATH="C:\JEROME"
JMPATH is automatically created if it does not exist. It's default value will
be the user's mail directory.
If there is a chance that more than one workstation will be logged into the same
NetWare user account, JMPATH must be set to a unique location for each
workstation.
4. Additional Novell Installation Option
A NetWare supervisor may use JM to create in the SYS:PUBLIC directory a
JMENU.DAT file that contains standard menu options for network users. Users can
import options from this menu to their own menu as follows:
1. Press INS from the JM Application list.
2. While cursor is highlighting MENU TEXT, press INS again.
3. The Standard Menu Options menu will appear, and the user may select a
menu option/definition to import.
4. Press ESC to return to the users personal menu, and the new option
(application) will be present.
5. JM Identifier Variables.
Identifiers are predefined key words recognized by JM. They represent textual
information that is variable. For example, the identifier %DAY_OF_WEEK
represents the literal string "Monday," "Tuesday," or whatever the current day
is.
Identifiers may be displayed (see DOS ECHO command), used in comparisons (see
DOS IF command), and used as program parameters.
JM identifiers are preceded by a percent sign (%), and will be replaced by their
corresponding text value upon batch file execution. They may appear anywhere in
the batch file. JM identifiers must be in all capitals.
Although JM identifier variables are not supported in DOS Batch files, they are
supported in JM batch files.
Example: This: ECHO Good %GREETING_TIME.
becomes: ECHO Good Afternoon.
6. General Purpose Identifier Variables
Identifier Text Value
%AM_PM am or pm
%GREETING_TIME Morning, Evening...
%HOUR 1 to 12
%HOUR24 00 to 23
%MINUTE 00 to 59
%SECOND 00 to 59
%DAY 01 to 31
%INPUT(prompt) User input
%DAY_OF_WEEK Monday, Tuesday...
%N_DAY_OF_WEEK 1 to 7 (1=Monday)
%MONTH 01 to 12
%MONTH_NAME June, May, etc
%YEAR 1983, 2016, etc
%SHORT_YEAR 83, 16, etc
7. NetWare-Specific Identifier Variables
Identifier Text Value
%LOGIN_NAME User's login name
%FULL_NAME User's Full Name
%STATION Logical Station #
%P_STATION Physical Station #
%OS MSDOS
%OS_VERSION V3.30 or V4.01
%MACHINE IBM PC, Victor9000, etc
%SMACHINE Short machine name
%MEMBER_OF() Yes, No, Error
%NEW_MAIL Yes, No
%USER_ID User's mail & Bindery ID#
8. DOS Identifier Variables
Normal DOS environmental variables and identifiers may also be used:
Identifier Text Value
%PATH% C:\DOS...
%COMSPEC% C:\COMMAND.COM
9. Sub-batch File Cautions:
When an option is selected, JeromeMenu creates a batch file called JMENU$$$.BAT,
and executes it. The last commands in the batch file contain information used
to restart JeromeMenu. If the batch file execution is interrupted, either by a
user-issued CTRL-BREAK, or an attempt to execute a batch file from within the
JMENU$$$.BAT, it may not be possible to automatically return to JeromeMenu.
If a batch file must be executed from within JMENU$$$.BAT, the batch file should
be CALLED rather than executed directly. For example, assume a batch file script
wishes to execute MYBATCH.BAT:
MYBATCH.BAT (Wrong way!)
CALL MYBATCH.BAT (Right way.)
JeromeEdit
JeromeEdit, (JEDIT), is a user-friendly text editor. It is ideal for editing
small files. It is very useful for editing AUTOEXEC.BAT, CONFIG.SYS and Novell
login scripts.
Using JEDIT
Type JEDIT followed by a filename at the DOS prompt.
Example: C:\>JEDIT C:\AUTOEXEC.BAT
If the file already exists, it will be read into the editor.
Example:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeEdit Vx.xx Wednesday January 23, 1991 9:06 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║@echo off ║
║cls ║
║prompt $p$g ║
║rxipx ║
║net3 ║
║F: ║
║login ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Use cursor keys and/or mouse to position cursor. Press F1 twice to get other
editor functions and key definitions.
To exit editor, press ESC. If text has not been modified, file will not be
saved. If text has been modified, JEDIT will display a "SAVE CHANGES" prompt.
Answer "YES" to save changed text, or "NO" to leave file unaltered.
DO
"DO" is a DOS Command/Login Script/Batch-enhancement utility. DO is NOT a TSR
(Terminate, Stay-resident) program, and does not tie up computer memory. It is
used to enhance user login screens, present random thoughts, and other "bells
and whistles."
Other programs similar to this one require a device driver called ANSI.SYS in
the CONFIG.SYS file. However, DO does NOT use the "Extended Screen and Keyboard
Control" driver, and therefore ANSI.SYS is not required.
Tutorial
DO is activated by typing DO followed by a command. A space must follow "DO"
and a space separates each command thereafter. The following is a list of all
the DO commands. (sss denotes a user-defined string of characters, n denotes an
integer.):
Commands:
HELP Displays this list.
THOUGHT [n THOUGHT] Displays thought # n.
TIMEDATE Displays current system time and date.
DO [sss DO] Processes commands in the file {sss}.
? [?sss] Displays string {sss}.
RND Replaces {n} as a random number.
X [n X] Loads X register with {n}.
Y [n Y] Loads Y register with {n}.
GO [n X n Y GO] Moves display cursor to position X,Y.
FOR [n FOR] Sets display foreground color to [n].
BCK [n BCK] Sets display background color to [n].
BDR [n BDR] Sets display border color to [n].
BLINK Sets display to blink mode.
CLS Clears screen to current foreground and background colors.
HOME Moves display cursor to position 1,1.
SOUND [n SOUND] Causes speaker to emit sound of freq. {n}. (0=off)
SOUNDn Causes speaker to emit noise # {n}.
BUG Displays a computer system bug.
PRINT Prints screen to LPT1:.
BAR [n BAR] Displays row of 80 characters, char is ASCII#{n}.
REBOOT ColdBoots PC. (Pulls the plug.)
2. Examples: C:\>DO CLS
This command will clear the screen.
C:\>DO BLUE BCK WHITE FOR CLS
This command will clear the screen to a blue background and a white foreground.
(White on blue.) Notice that you first specify the color (BLUE), and then where
the color is to go (BCK). The last thing that is specified is to clear the
screen to the specified colors of foreground (FOR) and background (BCK).
C:\>DO WHITE FOR BLUE BCK CLS
This command does exactly the same thing as the prior command. BCK may proceed
or follow the FOR command.
Command Reference
BAR
This command will display a row of 80 characters. The actual characters
displayed must be specified by the characters ASCII numeric code. The
characters will be displayed in the current foreground and background colors,
at the current display position. The following example displays 80 smiling
faces on an IBM PC CGA screen.
EXAMPLE: C:\>DO 1 BAR
BUG
It seems that all computer programs have bugs. The "DO" program is no
exception. The BUG command shows a "DO" program "BUG" in the current
foreground and background colors, at the current display cursor position.
EXAMPLE: C:\>DO BUG
BCK
This command sets the display foreground color.
EXAMPLE: C:\>DO RED BCK ?RED ?Background.
BDR
This command sets the CGA border color.
EXAMPLE: C:\>DO RED BDR
BLINK
This command modifies the specified foreground color to a flashing mode. The
BLINK command must be placed immediately before the FOR command. Text
displayed after this command will flash.
EXAMPLE: C:\>DO YELLOW BLINK FOR ?Now ?I ?blink.
CLS
This command clears the display to the current background and foreground
colors, and positions the display cursor at the HOME position.
EXAMPLE: C:\>DO RED FOR GREEN BCK CLS
DO
A long list of commands for the may become cumbersome to list on one command
line. An alternative method is to put the commands into a text file, one
command per line. "DO" can execute the commands in a text file as though
they were on the DOS command line.
EXAMPLE: C:\>DO FILENAME.EXT DO
(Where the file: FILENAME.EXT contains "DO" instructions.)
FOR
This command sets the display foreground color.
EXAMPLE: C:\>DO GREEN FOR "?This is green."
GO
This command positions the display cursor anywhere on the screen. First set
the X and Y registers to the screen coordinates, then GO.
EXAMPLE: C:\>DO 5 X 5 Y GO TIMEDATE
HELP
Displays a quick reference to all the DO functions in the current foreground
and background colors.
EXAMPLE: C:\>DO HELP
HOME
Moves the display cursor to {1,1} or home position. This command would be
the same as; DO 1 X 1 Y GO
EXAMPLE: C:\>DO HOME "?This is the top."
PRINT
This command has the same effect as SHIFT PrtSc. It dumps the content of the
screen to the printer (LPT1:).
EXAMPLE: C:\>DO PRINT
REBOOT
This command causes the PC to perform a system coldboot. It is equivalent to
switching off the power to your computer, then turning it back on again.
This command is not exactly equivalent to a warm boot Ctrl_Alt_Del.
EXAMPLE: C:\>DO REBOOT
RND
You may wish to replace a constant number with a random number. You can use
RND anywhere you would a number.
EXAMPLE: C:\>DO RND THOUGHT
SOUND
This command will start the speaker sounding at a specified pitch. The
speaker will not turn off until it receives a NOSOUND command, (even if you
leave the DO program).
EXAMPLE: C:\>DO 2000 SOUND
SOUNDn
There are several sounds, (Laser shots, etc.), that can be generated by the
DO program. (SOUND1, SOUND2, etc..).
EXAMPLE: C:\>DO SOUND1
THOUGHT
There are roughly 250 quotes, or thoughts, in the DO program. To display a
thought, using the current foreground and background color, enter a thought
number, then the command "THOUGHT."
EXAMPLE: C:\>DO 43 THOUGHT
The thought number can be replaced by "RND" to get a random thought.
EXAMPLE: C:\>DO RND THOUGHT
TIMEDATE
This command displays current system time and date at the current position
using the current foreground and background colors in the format: Tue Jan 01
01:48:31 1991
EXAMPLE: C:\>DO TIMEDATE
X, Y
These are general purpose registers, or memories that can be loaded with a
number. At present, the only command that accesses them is the GO command.
(See the GO command.)
EXAMPLE: C:\>DO RND X 5 Y
?
This command tells DO to display what follows at the current cursor position,
using the current foreground and background colors. No space follows the ?.
When the command is entered from the DOS command line, the string must be
within quotes ("?{string}"). If this command is executed from a DO file (see
the DO command) quotes should not be used.
COMMAND LINE EXAMPLE: C:\>DO "?Hello world!"
DO FILE EXAMPLE: ?Hello world!
DO Color Equivalences
The following table lists numbers that may be used to specify colors. The
color's macro equivalent may be used instead of a number;
{n} Actual Color DO Macro Equivalent
0 Black BLACK
1 Blue BLUE
2 Green GREEN
3 Cyan CYAN
4 Red RED
5 Magenta MAGENTA
6 Brown BROWN
7 White WHITE
8 Gray GRAY
9 Light Blue LTBLUE
10 Light Green LTGREEN
11 Light Cyan LTCYAN
12 light Red LTRED
13 Light Magenta LTMAGENTA
14 Yellow YELLOW
15 Bright White LTWHITE
JMESSAGE & JMSGCON
JMESSAGE & JMSGCON are message utilities for NetWare. These programs are NOT
TSRs (Terminate, Stay-Resident), and do not tie up computer memory.
JMSGCON is used by a network manager to define messages to be displayed. It is
usually executed from the DOS command line, or from a menu program such as JM.
JMESSAGE is used by network users to display messages. It may be executed from
the DOS command line, batch file, login script, or from a menu program such as
JM.
Most NetWare supervisors have a way to display messages to users as they log in.
This is done using the DISPLAY or FDISPLAY login-script commands. These
commands display a text file to the user who is logging in.
In theory, this approach seems adequate. In practice, users consider these
messages an annoyance. The same messages are displayed each time the user logs
in. Users rarely read these messages.
For example; a network supervisor enters the following line into the SYSTEM
LOGIN SCRIPT:
DISPLAY SYS:PROGRAMS\MESSAGE\BACKUP.MSG
The file contains the following:
FILESERVER WILL BE DOWN FRIDAY FOR BACKUP.
PLEASE LOGOUT BY 5:00PM. THANK YOU.
Each time users log into the fileserver, they will see the contents of the file.
They may read the message once, but it is ignored thereafter. Ignoring the
message is bad when the network supervisor decides to change the message:
FILESERVER WILL BE DOWN FOR BACKUP SATURDAY
FROM 8:00AM TO 10:00AM. THANK YOU.
Most users will not realize that the message has changed.
This is an oversimplification of the problem. There are many creative network
supervisors that have found ways to "poetically" display messages. Some methods
work better than others.
The MESSAGE program is a sure-fire method of getting a user's attention. Its
features include:
Messages are displayed no more than once a day to users, even if they login
many times.
Messages are displayed to a specific user group.
Messages may be assigned a specific starting and ending date.
Messages may be assigned to a specific day of week.
Messages may be flagged as Unique or Periodic.
JMSGCON Tutorial
Type JMSGCON at the DOS prompt.
Example: C:\>JMSGCON
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMessage Console Vx.xx Saturday January 26, 1991 9:11 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╔══════════════════════════════════════════╗░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ Message List ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╠══════════════════════════════════════════╣░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╚══════════════════════════════════════════╝░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
This is a list of defined messages. To create a new message, press INS
(INSERT).
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMessage Console Vx.xx Saturday January 26, 1991 9:13 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░┌────────────────────────────────────────────────────────────────────────────┐░
░│ Message detail │░
░├────────────────────────────────────────────────────────────────────────────┤░
░│ │░
░│ Title.......: Down Every Friday Night For Backup │░
░│ Frequency...: Periodic │░
░│ Start Date..: Saturday Jan. 26, 1991 │░
░│ End Date....: Wednesday Jan. 26, 2000 │░
░│ Day of week.: Friday │░
░│ Scope.......: EVERYONE │░
░│ Message File: z:\public\BACKUP.MSG │░
░│ Editor......: [INTERNAL] │░
░└────────────────────────────────────────────────────────────────────────────┘░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╚══════════════════════════════════════════╝░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
1. Message Parameters
Title: This is the JMSGCON message title. This title is not displayed as
part of the message. It is only used by JMSGCON to identify
messages.
Frequency: Messages may be displayed on a periodic basis, or only once. The
two values for this field are:
PERIODIC Causes message to be displayed once each day if
conditions are met.
UNIQUE Causes message to be displayed only once, when conditions
are met.
Start Date: Date that message will become active. Message will not be
displayed until this date.
End Date: Date that message will become obsolete. Message will not be
displayed after this date.
DayOfWeek: Day of week that message will be displayed. A specific day of week
may be used, or "Any Day" may be selected if message is to be
displayed without regard to the day of week.
Scope: This field contains the NetWare group that will view the message.
Only one group may be specified. Group EVERYONE is the default
scope.
MessageFile: Path & filename of the message. All messages are DOS Text files.
It is not required to define the message inside JMSGCON. Messages
may be created from any editor or word processor that can generate
a DOS Text file. By default, this field will have Z:PUBLIC\ as the
directory, the actual file name must be supplied.
Editor: By default, messages may be created and edited using a Text editor
built into JMSGCON. The default value of this field "[INTERNAL]"
caused the internal Text editor to be used. If you have a favorite
Text file editor, you may specify the filename of the editor in
this field. When you edit messages from JMSGCON, the specified
editor will be called.
For Example, if you wanted to use "JEDIT" instead of the internal editor, change
[INTERNAL] to JEDIT.After pressing INSERT and filling out the message title,
frequency, start date, end date, day of week, user scope, message file, and
preferred message editor, press ESC to return to the main list of messages.
Your new message title will appear;
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMessage Console Vx.xx Saturday January 26, 1991 9:11 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╔══════════════════════════════════════════╗░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ Message List ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╠══════════════════════════════════════════╣░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ Down Every Friday Night For Backup ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░║ │ ║░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░╚══════════════════════════════════════════╝░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
At this point, the message text may be created or edited by selecting the
particular message title and pressing . If the internal editor is used, a
screen such as the one below will follow, in which a message may be placed:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMessage Console Vx.xx Sunday January 27, 1991 3:26 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ Fileserver will be down each Friday from 5:30 to 7:30 pm for backup. ║
║ ║
║ Please be logged out each Friday evening by 5:15pm. ║
║ ║
║ If you have any questions, call John Doe. ║
║ ║
║ Thank you for your cooperation. ║
║ ║
║ M. I. S. Department. ║
║ ║
║ Good Day. ║
║ ║
║ . ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
When message text is complete, press ESC to return to message list.To examine or
modify a message definition, select the message from the list and press F3.
To remove a message definition, press DEL. Only the message definition is
deleted. The message file is not affected.
JMESSAGE Tutorial
JMESSAGE is activated by typing JMESSAGE at the DOS prompt, or by login script.
Examples: C:\>JMESSAGE (DOS PROMPT)
#JMESSAGE (LOGIN SCRIPT)
If the user has any outstanding messages, and conditions for messages are met,
Messages will be displayed.
Example Message:
Fileserver will be down each Friday from 5:30 to 7:30 pm for backup.
Please be logged out each Friday evening by 5:15pm.
If you have any questions, call John Doe.
Thank you for your cooperation.
M. I. S. Department.
Good Day.
.
Enter login name, or <ESC>:
The user will be prompted to Enter login name, or <ESC>:.
If the login name is entered correctly, the message will be considered "Signed
Off." Such messages are not redisplayed to the that user that day. If the
message was flagged as "UNIQUE," the message will never be redisplayed to the
user. If the message was flagged "PERIODIC" the message may be re-displayed on
another day if message conditions are met.
If the login name is not entered correctly, the message will be redisplayed each
time the user re-executes JMESSAGE, and message conditions are met. Pressing
at the prompt has the same effect as incorrectly entering users login name.
If ESC is pressed at the prompt, JMESSAGE terminates. It is assumed that the
user does not have time to read messages at this time, and messages are left in
a "Non-Signed-Off" state. Messages may be read by re-executing JMESSAGE.
JLOGOUT
JLOGOUT is a logout script executor for NetWare. It may be executed in place of
NetWare's LOGOUT command.
A logout script is created and stored in the user's Mail directory, (the same
place that a user's login script is located).
Although DOS batch files may be executed from JLOGOUT, JLOGOUT does not create
DOS batch files, or any other files for its own use during execution.
Creating a LOGOUT script
Before using JLOGOUT, a logout script must be created. Logout (and login)
scripts are located in SYS:MAIL directory, in the user's USER_ID subdirectory.
There are several methods to create a user's logout script. Two methods are
outlined below:
1. The Hard Way
The login script may be edited/created using a DOS text editor. Before
attempting to create the file, its location must be determined.
To find the location, the user's USER_ID must be determined. This may be done
using NetWare's SYSCON. From SYSCON, select USER INFORMATION. Select the
desired user, then select OTHER INFORMATION.
Example:
┌──────────────────────────────────────────────────────────────────────────────┐
│ NetWare System Configuration Vx.xx Tuesday January 29, 1991 7:34 pm │
│ User !ADAM On File Server JEROME │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╔═══════════════════════════════╗░░░░
░░░░░░╔════════════════════════╗═══════════║ User Information ║░░░░
░░░░░░║ User Names ║vailable To╠═══════════════════════════════╣░░░░
░░░░░░╠════════════════════════╣═══════════║ │Account Balance ║░░░░
░░░░░░║ │!ADAM │ ║ounting ║ │Account Restrictions ║░░░░
░░░░░░║ │!TPETRU │ ║nge Current║ │Change Password ║░░░░
░░░░░░║ │ALICE │ ║e Server In║ │Full Name ║░░░░
░░░░░░║ │ANDREWC │ ║up Informat║ │Groups Belonged To ║░░░░
░░░░░░║ │BRYANC │ ║ervisor Opt║ │Login Script ║░░░░
░░░░░░║ │CONKLINC │ ║r Informati║ │Managed Users And Groups ║░░░░
░░░░░░║ │DEREKC │ ║═══════════║ │Managers ║░░░░
░░░░░░║ │DORIANC │ ║░░░░░░░░░░░║ │Other Information ║░░░░
░░░░░░║ │GUEST ┌───────────────────────────────────────────────────────────┐░
░░░░░░║ │HEATHERC │Last Login: January 29, 1991 5:36:37 pm│░
░░░░░░║ │JEROME │File Server Console Operator: Yes │░
░░░░░░║ │MARJORIE │Maximum Server Disk Usage: Unrestricted │░
░░░░░░║ │MARNIEC │Disk Space In Use: 52,588 KBytes │░
░░░░░░╚═══════════│User ID: 05000001 │░
░░░░░░░░░░░░░░░░░░└───────────────────────────────────────────────────────────┘░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
The USER_ID is the number at the bottom of the window. The location of the
logout script file for the user in the example would be:
SYS:MAIL\5000001 (Any leading zeros on USER_ID should be ignored.)
To edit the logout script of the example user with the JEDIT text editor:
C:\>JEDIT SYS:MAIL\5000001\LOGOUT
2. The JM Way
If you are using JeromeMenu (JM) use the following menu script to edit the
logout script;
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Tuesday January 29, 1991 7:57 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
╔══════════════════════════════════════════════════════════════════════════════╗
║ Batch Commands: ║
╠══════════════════════════════════════════════════════════════════════════════╣
║@ECHO OFF ║
║JEDIT SYS:MAIL\%USER_ID\LOGOUT ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
║ Batch Commands: ... ║
╚══════════════════════════════════════════════════════════════════════════════╝
Example Logout Script
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeEdit Vx.xx Wednesday January 23, 1991 9:06 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║%CLS ║
║#LOGOUT ║
║#LOGIN ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
The above logout script will clear the screen, execute NetWare's logout program,
and then execute NetWare's login program.Using JLOGOUT
Type JLOGOUT followed by a filename at the DOS prompt.
Example: C:\>JLOGOUT
JLOGOUT may also be executed from JeromeMenu, (JMENU). Example:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu V1.11 Tuesday January 29, 1991 7:57 pm │
└──────────────────────────────────────────────────────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
╔══════════════════════════════════════════════════════════════════════════════╗
║ Batch Commands: ║
╠══════════════════════════════════════════════════════════════════════════════╣
║@ECHO OFF ║
║JLOGOUT ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
║ Batch Commands: ... ║
╚══════════════════════════════════════════════════════════════════════════════╝
JLOGOUT Script Identifier Variables.
Identifiers are predefined key words recognized by JLOGOUT. They represent
textual information that is variable. For example, the identifier %DAY_OF_WEEK
represents the literal string "Monday," "Tuesday," or whatever the current day
is.
Identifiers may be placed anywhere in the LOGOUT script, such as in DOS command
line parameters. Identifiers are preceded by a percent sign (%), and will be
replaced by their corresponding text value upon batch file execution.
Identifiers must be in all capitals.
Example: This: #LOGIN %LOGIN_NAME.
becomes: #LOGIN !ADAM.
(Assuming that the username of the user executing JLOGOUT is !ADAM).
General Purpose Identifier Variables
Identifier Text Value
%AM_PM am or pm
%GREETING_TIME Morning, Evening...
%HOUR 1 to 12
%HOUR24 00 to 23
%MINUTE 00 to 59
%SECOND 00 to 59
%DAY 01 to 31
%INPUT(prompt) User input
%DAY_OF_WEEK Monday, Tuesday...
%N_DAY_OF_WEEK 1 to 7 (1=Monday)
%MONTH 01 to 12
%MONTH_NAME June, May, etc.
%YEAR 1983, 2016, etc.
%SHORT_YEAR 83, 16, etc.
NetWare-specific Identifier Variables
Identifier Text Value
%LOGIN_NAME User's login name
%FULL_NAME User's Full Name
%STATION Logical Station #
%P_STATION Physical Station #
%OS MSDOS
%OS_VERSION V3.30 or V4.0
%MACHINE IBM PC, Victor9000, etc
%SMACHINE Short machine name
%MEMBER_OF() Yes, No, Error
%NEW_MAIL Yes, No
%USER_ID User's mail & Bindery ID#
NetList
NetList is used to generate reports from a NetWare fileserver bindery. It may
be used to get a complete list of users, groups, and other bindery objects.
Syntax
Type NetList followed by parameters at the DOS prompt.
Usage: NetList <parameter parameter ...>
1. Printable Fields
The following are the printable fields available in NETLIST. They may be placed
anywhere on the command line, in any order. Any of the field names may be
followed with a "width" specifier. The width is specified by appending a colon
':' to the end of the field name, followed by the numeric value which specifies
the column width. The order in which they appear on the command line dictates
the order of the report's columns:
?#
Line Counter. Use this field to number report lines from 1 to x, and to
display a final line count in the report footer. The default # field width
is 4 characters.
?NAME
Object Name. The object name is a user's login name, a fileserver's name, a
group's name, etc. The default NAME field width is 10 characters. An object
ID name can be up to 47 characters long. If objects there are with login
names, you may wish to lengthen this field using the ':' width specifier.
?ID#
Object ID Number. This is the bindery object ID number. It equates to a
user's MAIL subdirectory name. The default ID# field width is 8 characters.
?LID
Object Long Identification. This field displays the object's identification
property value. It equates to a user's or group's full name. The default
LID field width is 20 characters. An object's long identification can be up
to 127 characters long. If there are long identifications longer than 20
characters, you may wish to lengthen this field using the ':' width
specifier.
?A_BALANCE
Object's Account Balance. This field displays the object's ACCOUNT_BALANCE
(balance) property value, and to display a system total in the report footer.
It equates to a user's account balance. The default A_Balance field width is
12 characters.
?A_LIMIT
Object's Account Balance Limit. This field displays the object's
ACCOUNT_BALANCE (limit) property value. It equates to a user's account
balance limit. The default A_Limit field width is 12 characters.
2. Sort Fields
The following parameters are used to sort the NetList report. They may be
placed anywhere on the command line, in any order.
SORT=NAME
Report will be sorted by object name, (Login_Name).
SORT=ID
Report will be sorted by object ID number, (Mail directory).
SORT=DATE_TIME
Report will be sorted by user's last login date and time.
3. Format Parameters
The following parameters are used to format the NetList report. They may be
placed anywhere on the command line, in any order.
HEADER
Print report header; (i.e, field names).
FOOTER
Print report footer; (i.e, field totals). If specified, the HEADER is
automatically selected. Even if the HEADER parameter is not specified, the
HEADER will be printed if the FOOTER parameter is specified.
4. Scope Fields
The following parameters are used to limit the scope of a NetList report. They
may be placed anywhere on the command line, in any order:
!NAME
Object Name. If this field is not specified, the default '*' wild card will
be assumed. The following example parameter will list all objects that have
a user name that begins with the letter 'S':
NETLIST !NAME=S* ?NAME
!TYPE
Object Type. If this field is not specified, the default of User, (U or
0x0001), will be assumed. The following example parameter will list all
fileservers:
NETLIST !TYPE=FS ?NAME
Object Types:
Value Hex eq. Object
ADM 0X000B Administration
APS 0x0047 Advertising PrintServer.
ARQ 0x0008 Archive Queue.
ARS 0x0009 ArchiveServer.
FS 0x0004 FileServer.
GW 0x0006 Gateway.
GP 0x0002 Group.
JQ 0x000A Job Queue.
JS 0x0005 JobServer.
PS 0x0007 PrintServer.
Q 0x0003 Queue.
RBS 0x0026 Remote BridgeServer.
? 0x0000 Unknown.
U 0x0001 User.
* 0xFFFF Wildcard.
Examples
The following example lists all user login names and user's Bindery ID numbers.
Example: C:\>NETLIST ?Name ?ID#
The following example produces the same list, only it first lists the user's
Bindery ID, then lists the user's login name.
Example: C:\>NETLIST ?ID# ?Name
ATTACHED
ATTACHED is a DOS Command/Batch/script-enhancement utility for Netware. It is
used to verify a workstation's connection to a specified fileserver. Command
may be issued from the DOS command line, in a DOS BATCH file, login script, etc.
Syntax
ATTACHED.EXE requires least one parameter:
Usage: ATTACHED {fileServer} {/d}
{fileServer} Name of Novell-Netware fileserver.
{/d} Display flag, used to display whether or not the workstation
is connected to specified fileserver.
Example
The following example will display user's attachment to a Novell Fileserver
named "FS1":
C:\>ATTACHED FS1 /d
ATTACHED is very useful in a BATCH file. For example, a Network manager may
create a batch file that will execute a program based on a user's attachment to
a specific fileserver.
Assume: A network manager wants to write a batch file [GRUMDATA.BAT] that will
attach users to a second fileserver [FS2], run a program [GRUMDORK], and
then logout of the second fileserver [FS2]. The problem is that some of
the users who will execute the batch are already attached to the second
fileserver [FS2]. The following resolves the problem:
[GRUMDATA.BAT] @ECHO OFF
CLS
ATTACHED FS2
IF ERRORLEVEL 1 GOTO PREVCON
ATTACH FS2/GUEST
MAP H:=FS2/SYS:GRUMINFO
H:
GRUMDORK
F:
LOGOUT FS2
GOTO END
:PREVCON
MAP H:=FS2/SYS:GRUMINFO
H:
GRUMDORK
F:
:ENDFLUSHKB
FLUSHKB, is a DOS Command/Batch-enhancement utility. It is used to flush
characters from the computer's keyboard buffer. Command may be issued from the
DOS command line, or in a DOS BATCH file.
Syntax
FLUSHKB.EXE requires no parameters.
Usage: FLUSHKB
Example
The following example shows how to flush all keystrokes from the keyboard buffer
before entering a program:
[DOMENU.BAT] @ECHO OFF
FLUSHKB
MENUPROGMEMBER
MEMBER is a DOS Command/Batch/script-enhancement utility for NetWare. It is
used to verify a user's membership in a NetWare group. Command may be issued
from the DOS command line, in a DOS batch file, etc.
Syntax
MEMBER.EXE requires at least one parameter:
Usage: MEMBER {group} {/d}
{group} Name of Novell NetWare group.
{/d} Display flag, used to display whether or not user is in group.
Examples
The following example will display user's membership of the netware group
EVERYONE:
C:\>MEMBER EVERYONE /d
MEMBER is very useful in a batch file. For example, a NetWare supervisor may
create a batch file that will execute a program based on a user's group
membership:
[WORDPROC.BAT] @ECHO OFF
CLS
MEMBER wordperfect
IF ERRORLEVEL 1 WP
MEMBER word
IF ERRORLEVEL 1 WORD
MEMBER wordstar
IF ERRORLEVEL 1 WORDSTAR
REBOOT
REBOOT is a DOS Command/Batch-enhancement utility. It is used to restart a
computer from a "Power-on" state. Command may be issued from the DOS command
line, or in a DOS batch file.
Syntax
REBOOT.EXE requires one parameter:
Usage: REBOOT {COLD|WARM}
COLD Causes a cold restart, just as though the power was switched off
and back on again. Computer will count memory, etc.
WARM Causes a warm restart, just as though the "CTRL-ALT-DEL" keys were
pressed. This method is quicker than a cold restart, but will not
function in every situation.
Examples
The following example will cause the computer to restart, as though from a
"Power-On" state:
C:\>REBOOT COLD
The following example will cause the computer to restart, as though CTRL-ALT-DEL
were pressed:
C:\>REBOOT WARM
Assume: A network manager has set up a print server, using Novell's PSERVER.EXE
program. Using PCONSOLE, the network manager can issue a command that
will down the Print Server. This must be done, for example, when the
network manager needs to change the configuration of the print server.
After the manager has modified the print server's configuration, and has
instructed PCONSOLE to down the print server, he must go to the print
server's location and re-load the print server software.
The following print server AUTOEXEC.BAT file resolves this problem by
automatically restarting the print server, as though CTRL-ALT-DEL were
pressed:
[AUTOEXEC.BAT] @ECHO OFF
CLS
PROMPT $p$g
IPX
NET3
F:
PSERVER FS1 PS1
REBOOT WARM
Assume: User wants his computer to do a cold restart using JM
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:43 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║ Menu Text: 15 20 25 30 35 40 45 50 55 60 65 70 ║
║ REBOOT ║
╔══════════════════════════════════════════════════════════════════════════════╗
║ Batch Commands: ║
╠══════════════════════════════════════════════════════════════════════════════╣
║@ECHO OFF ║
║REBOOT COLD ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
RERUN
RERUN is a DOS Command/Batch-enhancement utility. It is used to re-execute a
program a given number of times. Command may be issued from the DOS command
line, or in a DOS BATCH file.
Syntax
RERUN.EXE requires at least two parameters, followed by option arguments.
Usage: RERUN {cycles} {command} {arguments}
{cycles} Number of times to execute program.
{command} Name of command, (or program) to be executed.
{arguments} Optional command arguments for executed program.
Examples
The following will produce 10 iterations of the DIR command:
C:\>RERUN 10 DIR
The following is will produce five iterations of the DIR command, and
demonstrates how to pass the optional '/W' argument to the DIR command:
C:\>RERUN 5 DIR *.EXE /W
STUFFKB
STUFFKB is a DOS Command/Batch-enhancement utility. It is used to stuff
characters into the computer's keyboard buffer. Command may be issued from the
DOS command line, or in a DOS batch file.
BAT_EXIT is a DOS Command/Batch-enhancement utility. It is used to terminate a
batch file, and to optionally stuff characters into the computer's keyboard
buffer. It is usually issued from within a DOS batch file.
Syntax
STUFFKB.EXE requires one parameter:
Usage: STUFFKB {key string}
BAT_EXIT.BAT requires no parameters, although one parameter is optional:
Usage: BAT_EXIT {key string}
Examples
Assume: A network manager wants some of his users to execute a batch file that
will execute a series of programs, and then log users off the network.
First, the manager put the following batch file in the public directory:
[LOGOFF.BAT] FUMDORK
EATROCKS
LOGOUT
The batch file works, but users would get an error message; BATCH FILE
MISSING. The problem is resolved as follows:
[LOGOFF.BAT] FUMDORK
EATROCKS
STUFFKB LOGOUT
Assume: The following is an example of a users AUTOEXEC.BAT file to log the user
into a Novell Network.
[AUTOEXEC.BAT] @ECHO OFF
CLS
PROMPT $p$g
IPX
NET3
F:
:LOOP
LOGIN
IF ERRORLEVEL 1 GOTO LOOP
Normally it works well, except when the fileserver is down for backup.
When the network is down, the user would like to execute a different
batch file, called AUXEXEC.BAT. The problem is resolved as follows:
[AUTOEXEC.BAT] @ECHO OFF
CLS
PROMPT $p$g
IPX
IF ERRORLEVEL 1 BAT_EXIT AUXEXEC
NET3
IF ERRORLEVEL 1 BAT_EXIT AUXEXEC
F:
:LOOP
LOGIN
IF ERRORLEVEL 1 GOTO LOOP
Assume: User wants to logout from JM:
┌──────────────────────────────────────────────────────────────────────────────┐
│ JeromeMenu Vx.xx Wednesday February 6, 1991 8:43 pm │
└──────────────────────────────────────────────────────────────────────────────┘
╔══════════════════════════════════════════════════════════════════════════════╗
║ Menu Text: 15 20 25 30 35 40 45 50 55 60 65 70 ║
║ LOGOUT ║
╔══════════════════════════════════════════════════════════════════════════════╗
║ Batch Commands: ║
╠══════════════════════════════════════════════════════════════════════════════╣
║@ECHO OFF ║
║BAT_EXIT LOGOUT ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝